Image enabled reject repair for check processing capture

ABSTRACT

A method and apparatus for processing a plurality of financial documents, comprising, a document processor, wherein, for each financial document, the document processor captures data encoded on the financial document and an image of the financial document during a prime pass, and assigns a prime pass sequence number to each financial document. The apparatus includes a computer database in which the prime pass data and image is stored in association with the prime pass sequence number for the financial document. The document processor is adapted to determine whether the financial document should be rejected because the data and document image needs to be repaired or the data only needs to be repaired. If the data and image needs to be repaired, the document processor, or a desktop scanner/reader, recaptures the data and image, assigns a recapture sequence number to the financial document, and the recaptured data and image is stored in the computer database in association with the recapture sequence number. An image repair application is adapted to permit an operator to locate a prime pass image that matches the recaptured image, and to repair the document image by visually comparing the recaptured image with the prime pass image. The repaired document image is then stored in the computer database in association with the corresponding prime pass sequence number.

[0001] A portion of this disclosure contains material that is subject tocopyright protection. The copyright owner consents to the reproductionof the disclosure, as it appears in the Patent and Trademark Officepatent files or records, but otherwise reserves all copyright rightswhatsoever.

[0002] 1. Field of the Invention

[0003] The present invention generally relates to an improved system andmethod for repairing items, such as deposit slips and associated checks,that have been rejected during check processing using image capture.

[0004] 2. Background of the Invention

[0005] Reject repair is a well known problem in high volume checkprocessing operations that are typically conducted by banks.Conventional approaches for repairing rejected items in check processingsystems involve downloading the rejected MICR codeline data to anoffline system for repair, followed by a re-submission of the linked ormatched MICR codeline data back to the check processing system. Theoffline system disadvantageously has to rehandle all of the physicalitems for correction. A disadvantage of this approach is that therecaptured image and MICR codeline data may not be matched to thecorrect prime pass item sequence number. This “mismatching” results inincorrect images delivered online or in statements. Another disadvantageof this approach (which is usually the result of a “piggyback” ormisoriented image) is the loss of the correct relationship of anyinserted item to their original position in the capture string, whichmay cause deposits to be out of balance and items to be credited to thewrong accounts. Thus, there remains a need for a check processing systemwhere the recaptured MICR codeline data and images for rejected items isassociated with the correct prime pass sequence number. There alsoremains a need for a check processing system that preserves the correctsequential relationship of MICR codeline data and images for inserteditems to the sequence of items established during the prime pass.

SUMMARY OF THE INVENTION

[0006] A method and apparatus for processing a plurality of financialdocuments, comprising, a document processor that captures data encodedon the financial documents and an image of the financial documentsduring a prime pass, and assigns a prime pass sequence number to eachfinancial document. The apparatus includes a computer database in whichthe prime pass data and image is stored in association with the primepass sequence number for the financial document. The document processoris adapted to determine whether the financial document should berejected because the data and document image needs to be repaired or thedata only needs to be repaired. If the data and image needs to berepaired, the document processor, or another reader/scanner, recapturesthe data and image, assigns a recapture sequence number to the financialdocument, and the recaptured data and image is stored in the computerdatabase in association with the recapture sequence number. An imagerepair application is adapted to permit an operator to locate a primepass image that matches the recaptured image, and to repair the documentimage by visually comparing the recaptured image with the prime passimage. The repaired document image is then stored in the computerdatabase in association with the corresponding prime pass sequencenumber.

[0007] The apparatus can be configured to allow the operator to repairthe prime pass image by visually comparing it with the recaptured imageand selecting either the prime pass image or the recaptured image.

[0008] If there is no prime pass image that corresponds to therecaptured image, the recaptured image is stored in the computerdatabase in correct relation to the financial sequence establishedduring the prime pass.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009]FIG. 1 is a diagram of a checking processing system in accordancewith the present invention.

[0010] FIGS. 2A-2C is a high level data flow diagram illustrating thelogic of the image repair application of the present invention.

[0011]FIG. 3 is a high level data flow diagram illustrating the logic ofthe keying application of the present invention.

[0012]FIG. 4 is an illustration of the logical relationship betweenprime pass MICR codeline data and images and recapture MICR codelinedata and images.

[0013]FIG. 5 is a screen shot of the user interface to the image repairclient application of the present invention.

[0014]FIG. 6 is a screen shot of the user interface to the keyingapplication.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENT

[0015] The system 10 in accordance with the present invention isillustrated in FIG. 1. Documents for processing 12, such as a check,deposit slip or other machine-readable document, are first physicallyprepared for batch processing. This includes removing paper clips,staples, rubber bands, etc. from the documents and arranging them intrays of batches with proper orientation and in proper order. A batch isa logical group of work, usually consisting of approximately 300documents. A batch can be a group of checks from another financialinstitution or a cut from a teller's machine. For each batch, a batchslip is typically encoded with the dollar total of all debit itemswithin the batch. Batches can optionally be divided it into smallergroups called subbatches, which are handled in the same way as a batch.

[0016] A block is the next higher level of control after the batch (andoptional subbatch). A block is a group of batches originating from thesame source, such as a cash letter originating from another financialinstitution or work originating from one branch or teller location.Blocks can be grouped together, each with its own block slip, into traysof approximately 3000 items.

[0017] The tracer group, the next higher level of control, consists of agroup of blocks. Tracer-group slips are placed in front of the documentsthat constitute the tracer group.

[0018] An entry is the highest level of control. By combining severaltracer groups, an entry is created, which is a convenient unit of workfor a document processor.

[0019] To take advantage of concurrent processing, that is, the abilityto start subsequent processing of items before entering all the items ofan entry, subsets can be specified within an entry. A subset consists ofa single tracer group. Distribution tasks can begin when the firstsubset is completed.

[0020] After the documents 12 are prepared for processing, they areready for prime-pass entry, which is the first task of physicalprocessing. An identification number of the entry, such as the first 4digits in the account-number field on the first tracer slip of theentry, is entered by an operator, as wells as parameters for sorting thedocuments and other parameters, such as the date, the amount, thecontrol number, the account number, and the routing and transit number.

[0021] The documents 12 are then fed into a document processor 14, whichis conventional. An exemplary document processor is available fromInternational Business Machines Corporation, New Orchard Road, Armonk,N.Y. 10504, and is known as the IBM3890/XP Series document processor,which is a high-speed, high-volume document processor that readsmagnetically-inscribed documents or optical-character documents.

[0022] The first documents that enter the document processor 14 are thetracer slips. Tracer slips maintain pass-to-pass control. The documentprocessor 14 routes them to either the rehandle or the reject pockets.The tracer slips serve to separate and identify the tracer groups withinthe pockets. The check imaging system 20 builds a record for each tracerslip selected to a pocket. The tracer records contain the item count anddollar total for each rehandle pocket used during this pass. The checkimaging system 20 uses the totals as a control for items as they reenterthe system on subsequent passes.

[0023] Tracer groups also can be used to divide a large entry intosubsets in order to take advantage of subset processing. To use subsetprocessing, it should be specified in the sort pattern, and it should bespecified that every tracer group signals the start of a new subset.

[0024] The document processor 14 reads the first group of tracer slips.It then reads the block slip, which identifies all related documents aspart of the block, and directs it to the reject pocket. The batch slip,which identifies all related documents as part of a batch, follows theblock slip and is also directed to the reject pocket. Subbatch slips, ifused, follow the batch slip. Placement of the subbatch slips iscontrolled by the operator, and can be placed at several intervalswithin a batch, because they simply provide an additional totalingfunction. The check imaging system 20 uses the encoded data from theblock, batch, and subbatch slips to balance the documents within theblock, batch, and subbatch and to identify the source of the documents.Block, batch, and subbatch slips can either precede or follow the itemsthat they control.

[0025] Divider slips separate items within each kill pocket intomanageable groups, or bundles. The sort pattern can be used to definethe size of each of these bundles. A kill pocket is a pocket in thedocument processor 14 that is assigned to items that are sent andremitted to another bank or destination without further sorting. Thesystem 10 uses the merge-feed unit of the document processor 14 to holdthe divider slips. When a bundle within a kill pocket reaches the limit,the document processor 14 automatically selects a divider slip from themerge-feed unit. Once the divider slip is in the input stream, thedocument processor 14 routes it to the correct kill pocket.

[0026] Individual items 12 follow the tracer, block, batch, and optionalsubbatch slips for capture of the magnetic ink character recognition(MICR) codeline data on the document. With respect to codeline data,capture means to read the codeline data that is inscribed on thedocument 12, to decode data, and to store the data. The documentprocessor 14 reads each item and a prime pass sequence number isassigned to and printed on each item. As the document processor 14 readsdata, the check processing controller 22 receives the data, creates acodeline data record and stores the codeline data record in a codelinedatabase 26. The check processing controller 22 is conventional. Anexemplary check processing controller is available from InternationalBusiness Machines Corporation, New Orchard Road, Armonk, N.Y. 10504, andis known as the IBM Check Processing Control System (“CPCS”). Thecodeline data record is the electronic representation of the codelinecaptured from a check, deposit, debit, credit, or control document. Theelectronic representation can include additional data to help identifythe record. The codeline database 26 contains records of all activedocument strings, and consists of two direct access data sets: adirectory index and a data record set.

[0027] Guided by the encoded data and the user specified sort program,the document processor 14 sorts the documents 12 to the correct pockets.The pockets are either onus, kill, reject, or rehandle, according to theuser specified sort pattern.

[0028] In the preferred embodiment, the check processing system 20includes a conventional imaging controller 28, which is available fromCheck Solutions Company, 8275 Tournament Drive, Suite 300, Memphis Tenn.38125, and is referred to as the ImagePlus High Performance TransactionSystem. The imaging controller 28 allows for the capture of the documentimage, which is stored by a conventional check imaging system 20 in animage database 30. Such a check imaging system is available from CheckSolutions Company, 8275 Tournament Drive, Suite 300, Memphis Tenn.38125, and is referred to as the Check Image Management System (“CIMS”).With respect to an image, capture means make a digitized image of adocument, and storing the image in one or more data sets. The imagingcontroller 28 preferably is capable of capturing the full documentimage, that is, an image of both sides of the document.

[0029] The check imaging system 20 creates a MICR codeline data recordin the codeline database 26 for each document 12 that passes through andis read by the document processor 14. Data, such as optical characterrecognition (OCR) data from remittances or a depositor's account number,is captured by the check imaging system 20 from the documents 12 thatare processed on the document processor 14. As is known in the art,additional software is required so that the document processor 14 canread the data and pass it to the check processing system 20.

[0030] During the processing of any entry, the document processor 14 canreject a document 12 for various reasons. In the preferred embodiment,the document processor 14 sorts rejected items into two pockets, asystem reject pocket (pocket-1) 16 and an alternate reject pocket(pocket-2) 18. A “rejected item” or a “reject” is a document that cannotbe read in its entirety by the document processor 14 or that failscertain predetermined tests.

[0031] Documents 12 are sorted to pocket-1 16 if they are automaticallyselected by the document processor 14. A document 12 is automaticallyselected because the document processor 14 has determined that thedocument is thicker or longer than a predetermined thickness or length,or the MICR codeline data is not read within a predetermined amount oftime. A document that is automatically selected for pocket-1 16 may be a“piggyback,” that is, a document that attaches itself to or overlaps oneor more other documents during processing by the document processor.

[0032] Documents are also sorted to pocket-1 16 if the documentprocessor 14 captured an image of the document, but no MICR codelinedata was captured. In cases where there is a document image but no MICRdata captured, there are at least two possible causes. First, thedocument image may be improperly oriented, that is, the image is flippedor rotated. Second, the document was printed using ink that does notconform with ANSI standard E13b for Print Specifications for MagneticInk Character Recognition, which may indicate that the document isfraudulent.

[0033] Documents 12 are sorted to pocket-2 18 if some valid MICRcodeline data was captured and they were not automatically selected tobe sorted to pocket-1 16. Such documents are likely to be correctlyoriented due to the fact that some MICR codeline data was captured.

[0034] Once the document processor 14 completes the prime passprocessing of an entry, the codeline data and images are retrieved fromthe codeline database 26 and the image database 30, respectively, andtransmitted to the reject repair server application 32.

[0035] Typically, the majority of rejected items are sorted to pocket-218, and the MICR codeline data can be repaired by a codeline data repairapplication 24 in a conventional manner, although the use of thephysical item is typically required for data input. An exemplarycodeline data repair application is available from InternationalBusiness Machines Corporation, New Orchard Road, Armonk, N.Y. 10504, andis known as the Online Reject Repair (“OLRR”) application. The keyingclient application 34 can be used to view the original prime pass imageand prompt the operator for high speed keying of the fields needingrepair. The codeline data repair application 24 performs editvalidations and automatically repairs the codeline data while preservingthe prime pass entry data relationships.

[0036] The pocket-2 rejects are then rehandled under the control ofcheck processing controller 22 so that distribution can occur withouthaving to recapture the items. These rehandled items are sorted topockets based on corrected codeline data and, therefore, they do nothave to be stripped and re-encoded.

[0037] It should be noted that pocket-2 rejected items with amount onlyerrors could be further sorted and directed to a keying application thatonly corrected the amount field, which would yield higher keying rates.

[0038] Pocket-1 rejected items are processed via the image repair clientapplication 36. FIGS. 2A-2C are high level flow diagrams that representsthe processing logic of the image repair client application. Turning toFIG. 2A, to start the processing of pocket-1 rejects, an operatorselects an entry for processing (block 100). Upon selection of an entry,the prime pass codeline data file and the prime pass document image filefor the rejected items, which were previously transmitted from the checkprocessing system 20 to the reject repair server application 32, arethen transmitted from the reject repair server application to the imagerepair client application (block 102). (The prime pass codeline datafile and the prime pass document image file are illustrated in FIG. 4.)The rejected pocket-1 items are then recaptured by the operator (block104). The rejected items can be recaptured in a batch mode or a singleitem at a time. In the preferred embodiment, the pocket-1 rejects arerecaptured using a desktop scanner, with a MICR codeline reader, such asa BUIC 1500 Back Office Check Scanner, which is in electroniccommunication with the image repair client application. The BUIC 1500Back Office Check Scanner is available from Digital Check Corporation,466 Central Avenue, Suite 31, Northfield, Ill. 60093. Prior torecapturing the rejected items, the items should be reconditioned bystraightening folded items, inverting upside-down items, flippingreversed items, separating “piggybacks,” and removing any residualstaples or rubber bands.

[0039] After recapturing the pocket-1 rejects, a recapture codeline datafile and a recapture image file is created, there being a recapturecodeline data record and a recapture image record for each recapturedreject (block 106). It should be noted that the codeline data record andthe image record, for both prime pass and recapture, are associated byuse of an sequence number and an image key. Next, the image repairclient application displays the first recapture image and codeline dataand the first rejected prime pass image and codeline data record (block108). The operator then reviews the prime pass images to locate a matchto the recaptured image (block 110). If the operator can locate a primepass image that matches the recapture image (block 111), by visuallycomparing the recapture image with the prime pass images, processingcontinues with logic group A. If the operator cannot locate a matchingprime pass image (block 111), processing continues with logic group B.

[0040]FIG. 2B illustrates the processing logic of logic group A. Theoperator was able to locate a matching prime pass image, and theoperator determines whether the recaptured image is acceptable (block112). Next, the operator determines whether to use the rescanned imageor the prime pass image (block 113). If the operator selects the primepass image, the operator then determines if the prime pass image iscorrectly oriented (block 114). If it is, processing continues withblock 118. If the image is not correctly oriented, the operatorre-orients the image (block 116) and processing then continues withblock 118. If necessary, the operator can re-orient the image byrotating or flipping the image

[0041] If the operator elects not to use the prime pass image (block113), the image is rescanned (block 115), and the operator thendetermines whether the rescanned image is acceptable (block 112). If therecapture image is acceptable, processing continues with block 118. Ifthe recapture image is not acceptable, the item is rescanned andprocessing continues from block 112, as described above.

[0042] After selecting the recaptured or prime pass image, therecaptured codeline data and selected image is associated with thecorresponding prime pass sequence number of the matched prime pass image(block 118). If there are more items to process (block 120), the imagerepair client application advances to the next item (block 122) andprocessing returns to block 110. If the are no more items to beprocessed, the corrected codeline data file and image file aretransmitted to the reject repair server application for editverification (block 124).

[0043]FIG. 2C illustrates the processing logic of logic group B. Becausethe operator cannot locate a matching prime pass image, the recaptureimage is tagged as an inserted item and the operator determines thecorrect sequential location of the inserted item by viewing the primepass images (block 126). If the recaptured image is acceptable (block128), the recaptured codeline data and the image of the inserted item isassociated with the corresponding prime pass sequence number that theinserted item follows (block 130) and processing continues with block120. If the recaptured image is not acceptable (block 128), it isrescanned (block 132) until it is acceptable.

[0044] In addition, the present system incorporates a keying application34 that interfaces with the codeline data repair application 24. FIG. 3is a high level flow diagram that represents the processing logic of thekeying client application. Both repaired pocket-1 items and pocket-2items are processed by the keying application 34. Processing begins byselection of any entry by the operator for keying edit (block 200). Thecorrected codeline data file and corrected image file completed by theimage repair client application 36 is transferred from the reject repairserver application 32 to the keying client application 34. The firstcodeline data record is then read by the keying application (block 202),and the codeline data record is sent to the codeline data repairapplication for processing (block 204). If the codeline data repairapplication determines that the codeline data record is acceptable(block 206), the keying application determines whether there are moreitems for processing (block 208). If there are more items forprocessing, control is transferred to block 204. If the codeline datarepair application determines that the codeline data record is notacceptable (block 206), a corrected image of the document correspondingto the codeline data is presented to the operator and any fields inerror are corrected manually (block 210). Processing then passes toblock 208.

[0045] If there are no more items for processing (block 208), thecorrected codeline data is sent to the reject repair server application(block 212), and the images previously corrected by the image repairclient application are then sent from the reject repair serverapplication to the image data base for permanent storage (block 214).

[0046] In the preferred embodiment, the keying application presents auser interface that is advantageously designed to allow high speedkeying with the codeline fields displayed under the check. The fields tobe keyed and the errors in the codeline data are displayed in color foreasy identification. The check size is controlled in two sizes(commercial or retail) so that they can be displayed as large aspossible.

[0047] The keying application also advantageously incorporates automaticprocesses for disqualified items and determining if the correction is acharacter replacement or full field replacement. The keying applicationkeeps track of all rejects accepted by the codeline data repairapplication so that if an operator needs to stop in the middle of anentry, or if an error occurs, an automatic restart can be accomplished.After the entries are corrected and the codeline data repair applicationcompletes processing for both pockets. The pocket-1 items would berepaired using strips and encoded using a power encoder, which isavailable from NCR Corporation, 1700 S. Patterson Blvd., Dayton, Ohio45479, and is referred to as the NCR 7780. In an alternative embodiment,the pocket-1 items can be re-primed on the check processing controller22 as a new entry with corrected code lines. The pocket-2 items can beprocessed on a power encoder, such as the NCR7780, with a hold and viewfeature. This allows the items to be controlled under the checkprocessing controller as a rehandle and the distribution and kill of theitem will be handled using the prime pass sequence numbers. The items donot have to be physically repaired since they can be sorted based onmatched corrected data or the hold and view feature can allow datacorrections. This eliminates the stripping process for 80-90% of therejects.

[0048]FIG. 4 is an exemplary illustration of the logical (not physical)relationship between prime pass MICR codeline data and images andrecapture MICR codeline data and images, and how the sequence of itemsare preserved by the image repair client application of the presentinvention in the event of a “piggyback.” In this example, three datarecords 221, 222 and 223, and three corresponding image records 231, 232and 233, were created during the prime pass. During recapture of theseitems, two new data records 202 and 203, and the corresponding imagerecords 212 and 213, were created. The extra two data and image recordsare contained in the recapture data file 200 and recapture image file210, but not in the prime pass data or image file, because during theprime pass, items represented by recapture data records 202 and 203 wereattached to the item represented by recapture data record 201.

[0049] As can be seen in the example illustrated in FIG. 4, the primepass data file 220 and the prime pass image file 230 are each comprisedof three records, 221, 222 and 223, and 231, 232 and 233, respectively.Each data record created during the prime pass is comprised of three (3)fields. The first field 220 a is the prime pass sequence number, whichuniquely identifies the position of the prime pass data record withinthe group of records comprising the prime pass data file. The secondfield 220 b is the MICR codeline data, and the third field 220 c is animage key. Each data record created during recapture contains the samethree (3) fields as for the data records created during the prime pass.

[0050] Similarly, each image record created during the prime pass iscomprised of three (3) fields. The first field 230 a is an image key.The association between data record for an item and the image record forthe same item is established and maintained by the image key. As can beseen in this example, the image key for each data record is identical tothe image key for each image record. The second field 230 b is the imagedata for the front of the item and the third field 230 c is the imagedata for the back of the item. Again, each image record created duringrecapture contains the same three (3) fields as for the image recordscreated during the prime pass.

[0051] During the matching process performed by the image repair clientapplication, when the front and back images for recapture record 201 arecompared to the front and back images for prime pass record 221, it willbe apparent that the front images are identical and that the back imagesare different. Thus, the operator knows that the item represented by thenext record in the recapture data file 202 was attached to the itemrepresented by the first record in the recapture data file 201 duringthe prime pass. Thus, the operator directs the image repair clientapplication to associate recapture data record 202 with prime pass datarecord 221. For the same reason, the recapture data record 203 is alsoassociated with prime pass data record 221. This will preserve thesequential relationship of the items represented by recapture datarecords 201, 202 and 203. It should also be noted that in this example,the back image of the item represented by recapture data record 203 willmatch the back image of the item represented by prime pass data record221.

[0052] Finally, the front and back images for the items represented byrecapture data records 204 and 205 match the front and back images forthe items represented by prime pass data records 222 and 223.

[0053]FIG. 5 is a screenshot 300 of a user interface to the image repairclient application of the present invention.

[0054]FIG. 6 is a screenshot 400 of a user interface to the keyingapplication of the present invention.

[0055] The description of the preferred embodiments contained hereindetails the many ways the present invention can provide its intendedpurposes. While several preferred embodiments are described, it isapparent that various changes might be made without departing from thescope of the invention.

What is claimed is:
 1. An apparatus for processing a plurality offinancial documents, comprising: (a) a document processor, wherein, foreach financial document, the document processor (i) captures dataencoded on the financial document and an image of the financial documentduring a prime pass, and (ii) assigns a first sequence number to eachfinancial document; (b) a computer database, wherein, for each financialdocument, the captured data and image is stored in the computer databasein association with the first sequence number for the financialdocument; (c) wherein, for each financial document, the documentprocessor is adapted to determine, responsive to the captured data andimages, whether the financial document is of a first type or a secondtype, wherein the first type is a document for which the data anddocument image needs to be repaired and the second type is a documentfor which the data needs to be repaired; (d) wherein, for each documentof the first type, the document processor recaptures the data encoded onthe financial document, recaptures an image of the financial document,and assigns a second sequence number to the financial document, therecaptured data and the recaptured image being stored in the computerdatabase in association with the second sequence number; and (e) a imagerepair application, wherein the image repair application is adapted topermit an operator to locate a captured image that matches therecaptured image, and to repair the document image by visually comparingthe recaptured image with the captured image; and (f) wherein therepaired document image is stored in the computer database inassociation with the first sequence number for the captured data.
 2. Theapparatus of claim 1 , wherein the image repair application isconfigured to allow the operator to repair the captured image byvisually comparing the captured image with the recaptured image andselecting either the captured image or the recaptured image.
 3. Theapparatus of claim 2 , wherein the image repair application isconfigured to permit the operator to repair the selected image byvisually comparing the captured image with the recaptured image andreorienting the selected image.
 4. The apparatus of claim 3 , whereinthe selected image is reoriented by rotating the captured image.
 5. Theapparatus of claim 3 , wherein the selected image is reoriented byflipping the selected image.
 6. The apparatus of claim 1 , wherein, foreach financial document of the first type for which there is arecaptured image, but no matching captured image, the recaptured imageis stored in the computer database in correct relation to the financialdocument sequence established during the prime pass.
 7. The apparatus ofclaim 1 , wherein, for each financial document, the document processoris adapted to determine whether the financial document is of the firsttype by determining whether the financial document exceeds apredetermined document thickness.
 8. The apparatus of claim 1 , wherein,for each financial document, the document processor is adapted todetermine whether the financial document is of the first type bydetermining whether the financial document exceeds a predetermineddocument size.
 9. The apparatus of claim 8 , wherein, the predetermineddocument size is comprised of a predetermined document length.
 10. Theapparatus of claim 8 , wherein, the predetermined document size iscomprised of a predetermined document height.
 11. The apparatus of claim1 , wherein, for each financial document, the document processor isadapted to determine whether the financial document is of the first typeif the data encoded on the financial document is not read within apredetermined amount of time.
 12. The apparatus of claim 1 , wherein,for each financial document, the document processor is adapted todetermine whether the financial document is of the first type if no datais read from the document.
 13. An apparatus for processing a pluralityof financial documents, comprising: (a) a first document processor,wherein, for each financial document, the first document processor (i)captures data encoded on the financial document and an image of thefinancial document during a prime pass, and (ii) assigns a firstsequence number to each financial document; (b) a computer database,wherein, for each financial document, the captured data and image isstored in the computer database in association with the first sequencenumber for the financial document; (c) wherein, for each financialdocument, the first document processor is adapted to determine,responsive to the captured data and images, whether the financialdocument is of a first type or a second type, wherein the first type isa document for which the data and document image needs to be repairedand the second type is a document for which the data needs to berepaired; (d) wherein, for each document of the first type, a seconddocument processor recaptures the data encoded on the financialdocument, recaptures an image of the financial document, and assigns asecond sequence number to the financial document, the recaptured dataand the recaptured image being stored in the computer database inassociation with the second sequence number; and (e) a image repairapplication, wherein the image repair application is adapted to permitan operator to locate a captured image that matches the recapturedimage, and to repair the document image by visually comparing therecaptured image with the captured image; and (f) wherein the repaireddocument image is stored in the computer database in association withthe first sequence number for the captured data.
 14. An apparatus forprocessing a plurality of financial documents, comprising: (a) adocument processor, wherein, for each financial document, the documentprocessor (i) captures data encoded on the financial document and animage of the financial document during a prime pass, and (ii) assigns asequence number to each financial document; (b) a computer database,wherein, for each financial document, the captured data and image isstored in the computer database in association with the sequence numberfor the financial document; (c) wherein, for each financial document,the document processor is adapted to determine, responsive to thecaptured data and images, whether the financial document is of a firsttype or a second type, wherein the first type is a document for whichthe data and document image needs to be repaired and the second type isa document for which the data needs to be repaired; (d) a keyingapplication, wherein the keying application is adapted to permit anoperator to repair the captured data by visually comparing the capturedimage with the captured data; and (e) the repaired data is stored in thecomputer database in association with the sequence number for thedocument.